chore(docs): align Mintlify production docs with tagged releases#31
Merged
ggonzalez94 merged 1 commit intomainfrom Feb 25, 2026
Merged
chore(docs): align Mintlify production docs with tagged releases#31ggonzalez94 merged 1 commit intomainfrom
ggonzalez94 merged 1 commit intomainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs-liveto the release commit on everyv*tag in the release workflowdocs-liveWhy
Mintlify production deploys from a branch, not a Git tag. This keeps live docs aligned with released binaries by promoting only tagged commits to
docs-live.Validation
Note
Medium Risk
Adds a forced
git push --forceto a shared branch during releases, which can overwrite history if misconfigured and may affect any consumers ofdocs-live.Overview
Updates the tagged release GitHub Action to force-sync the
docs-livebranch to the exactv*tag commit after GoReleaser runs, enabling Mintlify production docs to deploy from a branch that always matches the latest release.Documents the new docs publishing flow by noting that Mintlify should target
docs-live(inREADME.md/AGENTS.md) and adds a correspondingCHANGELOG.mdentry under Unreleased.Written by Cursor Bugbot for commit 6956766. This will update automatically on new commits. Configure here.